This is much clearer now. I'll have look and the goal is to merge asap.

In the meantime I will try to get a complete list of what is missing in case of rendering compared to the MapLibre Style Specs.

Just to clarify: my goal for now is only to ensure the minimum changes are made to the core library. The rest will come later.
I've started to make comments. Also, I'd like to regroup vector specific classes under vector package.
For example, SymbolState should be into vector/ui/state and so on. Another example:
SymbolComposer.kt into vector/ui/symbols
That will simplify the review. Could you do this?

Instead of making a ton of annoying comments, we can do it this way:
In addition to the vector package refactoring, could you please have a look at all the changes made to the core library, and remove the ones which aren't strictly necessary?
By doing this, when I'll do my final pass, I will know that the changes I see are changes you really want to make.

Sure, I will refactor it. Some of the changes I need to look into, because they were made prior my work. I think today or maybe tomorrow I should push the changes in a commit.

Ok no problem!

I made the changes and packed it again in a single commit. In this instance I added a minimal implementation of infinity scroll y to be able to revert all changes in library/src/commonMain/kotlin/ovh/plrapps/mapcompose/core/VisibleTilesResolver.kt compared to master.
There are now no changes in core only small changes in api, ui/state and MapUi.kt. New Files are all held in vector package.
Should I also move MapState.addVectorLayer() into a separate api package in vector package?

• kotlinx-datetime is used in a test that @jershell implemented to measure performance
• pbandk is used to decode Protobuf

I made the changes and packed it again in a single commit. In this instance I added a minimal implementation of infinity scroll y to be able to revert all changes in library/src/commonMain/kotlin/ovh/plrapps/mapcompose/core/VisibleTilesResolver.kt compared to master.

Good one. I haven't implemented infinity scroll y for practical reason. Do you see a use case? I would say this is out of scope for this feature.

Should I also move MapState.addVectorLayer() into a separate api package in vector package?

We can keep those in core indeed.

kotlinx-datetime is used in a test that @jershell implemented to measure performance

Alright, we just need to make sure it's added as testImplementation. My comment was on kotlinx-datetime only.

Thanks

Good one. I haven't implemented infinity scroll y for practical reason. Do you see a use case? I would say this is out of scope for this feature.

Sorry, I meant infinite scroll x

Alright, we just need to make sure it's added as testImplementation. My comment was on kotlinx-datetime only.

It is added unter commonTest.dependencies.